|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Iskandara Cho
   |
Posted - 2008.12.27 17:20:00 -
[1]
Hi,
I would like to use yapeal to pull the personal information for my 3 alts as well as for my corporation, but I am having more than a little difficulty figuring out what I need to modify or not in the .ini file. Then there is the question of where I find the information needed for the registered characters and corporations.
A little help?
|
Iskandara Cho
|
Posted - 2008.12.28 14:38:00 -
[2]
Hi,
Thanks, that did help.
I've gone through your sample.ini file and come up with two separate documents:
An Example yapeal.ini for a single database and a first pass at Documentation for the yapeal.ini file.
If you could take a look at them and see if I've made any mistakes I'd be grateful.
I also ended up with a few questions:
 What is the behaviour of conflicting settings between the database and the database-xxx "active" fields?
What is the database named in any dbname field used for if the active field is set to FALSE? ie is it necessary to have a db name in the default section if the db-xxx sections have named db's?
Should each of the sub-db's have the same structure as the main db (as defined by the sql file provided)?
Does the username:password pairing need to be the same across all databases? Though there is a field in each db-xxx section they all share the same name "writer". If there is a pairing in the default Db section and a different pairing in a database-xxx section, which takes precedent?
Is the required section [DEBUGGING] really called [TRACING]?
Thanks!
|
Iskandara Cho
|
Posted - 2008.12.29 08:22:00 -
[3]
Edited by: Iskandara Cho on 29/12/2008 08:26:37
Thanks for the answers Dragonaire.
docs and sample ini files in a zip
It seems eve files didn't think they were appropriate content, so I've tried it as a zip. Let me know if there are still problems and I'll find another host.
|
Iskandara Cho
|
Posted - 2008.12.29 21:35:00 -
[4]
Edited by: Iskandara Cho on 29/12/2008 21:54:37
If these don't work I will resort to carrier pigeon...
First pass at documentation
Sample single db .ini
I pulled the latest files from subversion, reuploaded them, and again tried running the script from the command line with the same result.
The line in question (line 101 of the current file) reads:
$cachetypes = array('tableName' => 'C', 'ownerID' => 'I', 'cachedUntil' => 'T');
is it possible that something in my .ini file is causing this error?
For that matter, I am not sure I am calling the script properly.. what should my command line read for proper execution?
Thanks!
|
Iskandara Cho
|
Posted - 2008.12.30 07:21:00 -
[5]
Glad you found the docs useful.
I've pulled the backend file again, checked the ini file thrice, and I'm still getting the error about an unexpected { on line 101...
|
Iskandara Cho
|
Posted - 2008.12.31 11:58:00 -
[6]
No joy 
I've completely deleted the installation on my web server, updated from SVN, deleted the databases, ans started from scratch.
1) Uploaded files to server
2) edited ini file to new db info
3) ran script (php eve-api-pull.php)
4) Get an unexpected { on line 101 error
|
Iskandara Cho
|
Posted - 2009.01.05 02:20:00 -
[7]
Still no joy. I've contacted my server provider to see if they can shed any light on the problem. I'll keep you posted.
|
Iskandara Cho
|
Posted - 2009.01.05 09:21:00 -
[8]
Nope, no logs, it never gets to the point of actually executing anything.
I've heard back from support, and they said there is nothing they can do with 3rd party scripts. Not unusual I guess, but still kinda frustrating. I've sent you an email with the url to the phpinfo for my server.
Thanks for the help.
|
Iskandara Cho
|
Posted - 2009.01.16 22:11:00 -
[9]
Edited by: Iskandara Cho on 16/01/2009 22:11:06
Well, I guess I'll just toss my work thus far. Ah well.
Still, its nice to know we'll have an installer soon.
Also check Google Talk not gchat, they are different things. |
Iskandara Cho
|
Posted - 2009.01.17 00:21:00 -
[10]
Since IGB pages work out of game as well, there is no reaon to duplicate the work. I'll just take the hit and look forward to the install script being done.
|
|
|
|
|
| |
|